home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19980424-19980901
/
000422_news@newsmaster….columbia.edu _Mon Aug 31 15:27:32 1998.msg
< prev
next >
Wrap
Internet Message Format
|
1998-08-31
|
3KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id PAA05647
for <kermit.misc@watsun.cc.columbia.edu>; Mon, 31 Aug 1998 15:27:31 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id PAA04677
for kermit.misc@watsun; Mon, 31 Aug 1998 15:27:31 -0400 (EDT)
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: [Q] SOCKS4 and Kermit
Date: 31 Aug 1998 19:27:29 GMT
Organization: Columbia University
Lines: 45
Message-ID: <6setf1$qoh$1@apakabar.cc.columbia.edu>
References: <Pine.A32.3.91.980831113020.14450A-100000@kissel.spicerack.ibm.com>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:9153
In article <Pine.A32.3.91.980831113020.14450A-100000@kissel.spicerack.ibm.com>,
<kissel@kissel.spicerack.ibm.com> wrote:
: Does C-Kermit 6.0 have some sort of built-in support for SOCKS4 protocol?
:
Yes, if you build it in a certain way, described in Section 8.1.1 of the
ckccfg.doc file:
8.1.1. Firewalls
There exist various types of firewalls, set up allow separate users of an
internal TCP/IP network from the great wide Internet. Of course, this could
be accomplished most easily and safely by simply not connecting the internal
network to the Internet, but in many cases some restricted forms of access are
needed. Thus a "firewall" is set up to allow only authorized accesses.
One firewall method is called SOCKS, in which a proxy server allows users
inside a firewall to access the outside world, based on a permission list
generally stored in a file. SOCKS is enabled in one of two ways. First, the
standard sockets library is modified to handle the firewall, and then all the
client applications are relinked (in systems where linking is not dynamic)
with the modified sockets library. The APIs are all the same, so the
applications do not need to be recoded or recompiled.
In the other method, the applications must be modified to call replacement
routines, such as Raccept() instead of accept(), Rbind() instead of bind(),
etc, and then linked with a separate SOCKS library. This second method is
accomplished in C-Kermit by including -DCK_SOCKS in your CFLAGS, and also
adding:
-lsocks
to LIBS, or replacing -lsockets with -lsocks (depending on whether the socks
library also includes all the sockets entry points).
Explicit firewall support can, in general, not be a standard feature or a
feature that is selected at runtime, because the SOCKS library tends to be
different at each site -- local modifications abound.
The ideal situation occurs when firewalls are supported by the first method,
using dynamically linked sockets-replacement libraries; in this case, all your
TCP/IP client applications will negotiate the firewall transparently.
(end quote)
- Frank